Live test pipeline setup - #16213
Conversation
|
/azp run java - metricsadvisor - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
b0aff4a to
ac41a80
Compare
|
/azp run java - metricsadvisor - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run java - metricsadvisor - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
f688f48 to
c880bfb
Compare
There was a problem hiding this comment.
reported as service issue #_53
70a6f2b to
799cb08
Compare
1f4323c to
064d178
Compare
064d178 to
c9ee939
Compare
| } finally { | ||
| Mono<Void> deleteAnomalyAlertConfiguration | ||
| = client.deleteAnomalyAlertConfiguration(alertConfigurationId.get()); | ||
| StepVerifier.create(deleteAnomalyAlertConfiguration).verifyComplete(); |
There was a problem hiding this comment.
In finally should we attempt to clean up the resource only if the alertConfigurationId has a value (which means creation succeeded).
There was a problem hiding this comment.
the same comment for other applicable places we do the cleanup in finally.
| <configuration> | ||
| <systemPropertyVariables> | ||
| <!-- Parallel runs disabled due to subscriber timeout issue causing failures in tests. --> | ||
| <junit.jupiter.execution.parallel.enabled>false</junit.jupiter.execution.parallel.enabled> |
There was a problem hiding this comment.
Should leave a TODO to determine the root cause and fix this.
3954149 to
9b8f1e1
Compare
3 participants
Configure the live test pipeline to use the shared resources from the test subscription.
Pull changes from core redactor for empty value redaction bug fix.
Live test pipeline - https://dev.azure.com/azure-sdk/internal/_build/results?buildId=599834&view=results